Skip to content

Custom port support in Terminal manager#1459

Merged
RohitKushvaha01 merged 2 commits intoAcode-Foundation:mainfrom
RohitKushvaha01:terminal-custom-port
Jul 27, 2025
Merged

Custom port support in Terminal manager#1459
RohitKushvaha01 merged 2 commits intoAcode-Foundation:mainfrom
RohitKushvaha01:terminal-custom-port

Conversation

@RohitKushvaha01
Copy link
Copy Markdown
Member

@RohitKushvaha01 RohitKushvaha01 commented Jul 27, 2025

Terminal is useless for plugins if we cannot connect to custom axs ports

@UnschooledGamer
Copy link
Copy Markdown
Member

I can't tell if Rohit, Is Describing a PR, or giving critics.

Copy link
Copy Markdown
Member

@UnschooledGamer UnschooledGamer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@RohitKushvaha01 RohitKushvaha01 merged commit bec1532 into Acode-Foundation:main Jul 27, 2025
2 checks passed
@RohitKushvaha01 RohitKushvaha01 deleted the terminal-custom-port branch July 27, 2025 08:34
scrollOnUserInput: true,
rows: options.rows || 24,
cols: options.cols || 80,
port: options.port || 8767,
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure but this might create injection vulnerabilities ig. Also it should be passed as number or whatever is expected type of it.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The purpose is to let plugin developers start terminal sessions that connect to their own AXS instances. So yes, it's technically an injection vulnerability but intended

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants